Add bones-stale-branches command #60
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This command lists all stale branches in a repository. If you're in a repository with a .nengobones.yml, it will use the provided information. You can also pass a repo on the command line. Some known issues: - In order to avoid rate limiting, you must provide a Github username and personal access token as environment variables. - The call to the list of branches is not properly paginated, so only the first chunk of branches is fetched properly.
|
It's straightforward to view stale branches in Github. Is that sufficient? |
|
The idea with something like this is that we would use it as part of an automated process. But yeah not necessarily convinced it's a process we care about at this point. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This command lists all stale branches in a repository. If you're in a repository with a .nengobones.yml, it will use the provided information. You can also pass a repo on the command line.
Some known issues:
Motivation and context:
In looking at nengo/nengo#1485 I wondered if this is the kind of thing we should do regularly (remove stale branches). Since we already have the
bones-pr-numberscript, I thought this might be pretty straightforward. Unfortunately it was not, so before putting more time into it, we should figure out if this is something we actually want.How has this been tested?
Ran the command for Nengo Bones and Nengo Core.
How long should this take to review?
Types of changes:
Checklist: